home *** CD-ROM | disk | FTP | other *** search
- From: ajay@lehman.com (Ajay Kamdar)
- Message-ID: <199604031701.MAA16591@jabba.lehman.com>
- X-Original-Date: Wed, 3 Apr 1996 12:01:56 -0500
- Path: in2.uu.net!bounce-back
- Date: 03 Apr 96 17:25:19 GMT
- Approved: fjh@cs.mu.oz.au
- Subject: Re: delete vs incomplete class type
- Newsgroups: comp.std.c++
- References: <sjcDownA7.6FA@netcom.com> <4jcdp0$b3p@venus.mcs.com> <sjcDp7BEy.3J4@netcom.com> <3160CA2D.646FFC15@cantrip.org>
- Organization: Lehman Brothers, Inc.
- X-Auth: PGPMoose V1.1 PGP comp.std.c++
- iQBFAgUBMWK0i+EDnX0m9pzZAQGbIwF9E8gm+pH7cGMf2rbN0ZJVfnu/vL93q8f+
- pj8rLZQWOUa/CNa4pYYD2TV6F64AQfT+
- =s2iA
-
- In article <3160CA2D.646FFC15@cantrip.org>,
- Nathan Myers, http://www.cantrip.org/ <ncm@cantrip.org> wrote:
- >Steven Correll (sjc@netcom.com) wrote:
- >>
- >> I don't see how a compiler could avoid noticing that it hasn't a clue what
- >> destructor to invoke at compilation time. Is there a reason ... not to
- >> require the compiler to diagnose this as an error, instead of allowing
- >> it to fault at execution time?
- >
- >I have to agree with Steven ... it's silly to talk about preserving
- >legacy C code that has "delete" statements in it. Given the great
- >difficulty in finding bugs introduced this way, and the great ease of
- >introducing them accidentally through inclusion errors, we certainly
- >should change something.
- >
- >Fortunately fixing this would be a restriction, not an extension,
- >and thus is still conceivable in this round of standardization.
-
- So are you volunteering to champion a formal proposal to the
- committee to add this restriction in this round of standardization?
-
- Although it doesn't count in the committee, you do have my vote.
-
- ---
- Ajay Kamdar | Email: ajay@lehman.com | Standard Disclaimer
- Lehman Brothers | Phone: (201) 524-5048 |
- ---
- [ comp.std.c++ is moderated. To submit articles: try just posting with ]
- [ your news-reader. If that fails, use mailto:std-c++@ncar.ucar.edu ]
- [ FAQ: http://reality.sgi.com/employees/austern_mti/std-c++/faq.html ]
- [ Policy: http://reality.sgi.com/employees/austern_mti/std-c++/policy.html ]
- [ Comments? mailto:std-c++-request@ncar.ucar.edu ]
-